Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v24.2.x] CORE-7338 license: add metric #23466

Conversation

pgellert
Copy link
Contributor

@pgellert pgellert commented Sep 24, 2024

Backport of PR #23367

Fixes #23455

Conflict was on the storage test bazel BUILD file which was missing the unit test configs on this branch.

Expose the expiration as a time_point.

(cherry picked from commit 78de1c7)
These two fixture tests create multiple `feature_table`s at the same
time. This commit disables emitting metrics on these tests to prevent
double metric registration errors in the follow up commit of this PR.

(cherry picked from commit 1c8f66b)
Adds a metric to allow easier monitoring of when the enterprise license
is going to expiry.

The dependency on the `security` module existed even previously in the
bazel build but it was missing from the cmake build.

(cherry picked from commit edb5f48)
Adds a bazel build for the features module.

The include for base/vlog.h was unused, so it was removed instead of
adding a dependency.

(cherry picked from commit c44d9d8)
Adds an integration test for the license expiry metric.

(cherry picked from commit baece2c)
@pgellert pgellert added this to the v24.2.x-next milestone Sep 24, 2024
@pgellert pgellert added the kind/backport PRs targeting a stable branch label Sep 24, 2024
@pgellert pgellert self-assigned this Sep 24, 2024
@pgellert pgellert requested review from a team and andijcr and removed request for a team September 24, 2024 17:11
@pgellert pgellert marked this pull request as ready for review September 24, 2024 17:11
@pgellert pgellert requested review from BenPope and oleiman and removed request for andijcr September 24, 2024 17:11
@@ -0,0 +1,17 @@
load("//bazel:test.bzl", "redpanda_cc_btest")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll note that I'm not really clear on the guidance with respect to backporting BUILD files. I heard Noah say in core panda that it's not necessary, but I don't have a good sense of whether we should actively avoid doing it.

I don't think there's any harm in it, but it might be worth asking

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's my understanding as well. I've checked, and there's a thread in Slack saying that we only care about the bazel build on the dev branch (and 25.1 in the future).

Copy link
Member

@oleiman oleiman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@pgellert pgellert merged commit fe64fae into redpanda-data:v24.2.x Sep 25, 2024
20 checks passed
@BenPope BenPope modified the milestones: v24.2.x-next, v24.2.6 Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/redpanda kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants